-
Notifications
You must be signed in to change notification settings - Fork 550
Move examples/models/... out of the torch
namespace
#5318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/5318
Note: Links to docs will display an error until the docs builds have been completed. ❌ 5 New Failures, 1 Cancelled Job, 1 Unrelated FailureAs of commit 39b248c with merge base 67be84b ( NEW FAILURES - The following jobs have failed:
CANCELLED JOB - The following job was cancelled. Please retry:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D62591348 |
This pull request was exported from Phabricator. Differential Revision: D62591348 |
0e125dc
to
ada5783
Compare
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Differential Revision: D62591348
This pull request was exported from Phabricator. Differential Revision: D62591348 |
ada5783
to
fc13f26
Compare
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Differential Revision: D62591348
This pull request was exported from Phabricator. Differential Revision: D62591348 |
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Differential Revision: D62591348
fc13f26
to
fcf9102
Compare
This pull request was exported from Phabricator. Differential Revision: D62591348 |
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Differential Revision: D62591348
fcf9102
to
2b56aa3
Compare
This pull request was exported from Phabricator. Differential Revision: D62591348 |
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Reviewed By: larryliu0820 Differential Revision: D62591348
2b56aa3
to
a899417
Compare
This pull request was exported from Phabricator. Differential Revision: D62591348 |
a899417
to
304b4ba
Compare
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Reviewed By: larryliu0820 Differential Revision: D62591348
This pull request was exported from Phabricator. Differential Revision: D62591348 |
304b4ba
to
16def7e
Compare
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Reviewed By: larryliu0820 Differential Revision: D62591348
This pull request was exported from Phabricator. Differential Revision: D62591348 |
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Reviewed By: larryliu0820 Differential Revision: D62591348
16def7e
to
8558bb9
Compare
This pull request was exported from Phabricator. Differential Revision: D62591348 |
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Reviewed By: larryliu0820 Differential Revision: D62591348
8558bb9
to
d56e800
Compare
Summary: Pull Request resolved: pytorch#5318 The code under examples/... is a proxy for user code, and users should never declare code under the `torch::` or `executorch::` namespaces. Move this code under the `example::` namespace to make it more clear that users should use their own namespaces when writing code like this. I made one non-mechanical change in llama_tiktoken.h: we should always use `enum class` to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase. Tests: Should be a no-op; CI passes. Prints no output: ``` find examples/models -type f | xargs grep "namespace torch" find examples/models -type f | xargs grep "namespace executorch" ``` Build llava_main: ``` bash .ci/scripts/test_llava.sh ``` Reviewed By: larryliu0820 Differential Revision: D62591348
This pull request was exported from Phabricator. Differential Revision: D62591348 |
d56e800
to
39b248c
Compare
This pull request has been merged in 262dfc0. |
Fix the build errors I introduced in pytorch#5318 Test Plan: Build the model using the instructions at https://github.com/pytorch/executorch/blob/main/examples/models/phi-3-mini/README.md
Fix the build errors I introduced in pytorch#5318 Test Plan: Build the model using the instructions at https://github.com/pytorch/executorch/blob/main/examples/models/phi-3-mini/README.md
Summary: Fix the build errors I introduced in #5318 Pull Request resolved: #5513 Test Plan: Built the model using the instructions at https://github.com/pytorch/executorch/blob/main/examples/models/phi-3-mini/README.md Reviewed By: helunwencser Differential Revision: D63133231 Pulled By: dbort fbshipit-source-id: 81d5402e76fd86c919a13a1b1b83687feca72ab7
Summary: Fix the build errors I introduced in #5318 Pull Request resolved: #5513 Test Plan: Built the model using the instructions at https://github.com/pytorch/executorch/blob/main/examples/models/phi-3-mini/README.md Reviewed By: helunwencser Differential Revision: D63133231 Pulled By: dbort fbshipit-source-id: 81d5402e76fd86c919a13a1b1b83687feca72ab7 (cherry picked from commit 8618607)
Fix phi-3-mini build (#5513) Summary: Fix the build errors I introduced in #5318 Pull Request resolved: #5513 Test Plan: Built the model using the instructions at https://github.com/pytorch/executorch/blob/main/examples/models/phi-3-mini/README.md Reviewed By: helunwencser Differential Revision: D63133231 Pulled By: dbort fbshipit-source-id: 81d5402e76fd86c919a13a1b1b83687feca72ab7 (cherry picked from commit 8618607) Co-authored-by: Dave Bort <[email protected]>
Summary:
The code under examples/... is a proxy for user code, and users should never declare code under the
torch::
orexecutorch::
namespaces.Move this code under the
example::
namespace to make it more clear that users should use their own namespaces when writing code like this.I made one non-mechanical change in llama_tiktoken.h: we should always use
enum class
to avoid polluting the parent namespace, and enum values should follow UpperSnakeCase.Differential Revision: D62591348